[WIP][SPARK-50983][SQL] Support Nested Correlated Subqueries for Analyzer #49660
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
cc: @agubichev for review |
|
WIP:
|
AveryQi115
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Analyzer is using same outer plan context to resolve subquery if there is outer plan context defined, otherwise it uses the outer plan provided by the function as context.
Add unresolvedOuterAttrs argument for SubqueryExpression to record outerAttrs cannot be resolved in the immediate parent query but might be resolved in other ancestor queries.
Why are the changes needed?
Support Nested Correlated Subqueries for Analyzer needed for decorrelating nested correlated subqueries.
Does this PR introduce any user-facing change?
yes, add a user-facing config to enable analyzer to support nested correlated subqueries.
How was this patch tested?
WIP
Was this patch authored or co-authored using generative AI tooling?
No